{ "status": "ok", "feed": { "url": "https://blog.centos.org/feed/", "title": "Blog.CentOS.org", "link": "https://blog.centos.org/", "author": "", "description": "News, views, and reports on CentOS", "image": "https://blog.centos.org/wp-content/uploads/2018/09/centos-logo-348x350-c-150x150.png" }, "items": [ { "title": "June 2024 News", "pubDate": "2024-06-27 16:05:53", "link": "https://blog.centos.org/2024/06/june-2024-news/?utm_source=rss&utm_medium=rss&utm_campaign=june-2024-news", "guid": "https://blog.centos.org/?p=3191", "author": "shaunm", "thumbnail": "", "description": "June 2024 News CentOS Linux 7 will be EOL on June 30. Please migrate to CentOS Stream 9 or another suitable option. Various services that used CentOS Linux 7 will be retired at the end of June. In particular, the CentOS Forums will be shut down, and redirect to the CentOS category on Fedora Discourse. […]", "content": "\n

June 2024 News

\n\n

\nKmods SIG\n

\n

The Kmods SIG focuses on packaging and maintaining kernel modules for CentOS Stream and Enterprise Linux.

\n\n

\nVirtualization SIG\n

\n

The Virt-SIG aims to deliver a user-consumable full stack for virtualization technologies that want to work with the SIG. This includes delivery, deployment, management, update and patch application (for full lifecycle management) of the baseline platform when deployed in sync with a technology curated by the Virt-SIG..

\n\n

\nISA\n

\n

The ISA SIG explores ways to deliver optimized package builds targeted at instruction set architecture (ISA) variants of architectures already supported by CentOS.

\n\n

\nAlternative Images SIG\n

\n

The Alternate Images SIG's goal is to build and provide alternate iso images for CentOS Stream.

\n\n

\nArtwork SIG\n

\n

The CentOS Artwork SIG exists to produce The CentOS Project Visual Identity.

\n\n\n

\nIntegration SIG\n

\n

Provide a shared space to develop and maintain tooling and knowledge base on collaborative gating and testing of CentOS Stream updates before they are published to CentOS mirrors. This includes both - package-level and compose-level integration.

\n\n", "enclosure": {}, "categories": [ "Newsletter" ] }, { "title": "CentOS Board Meeting Recap, June 2024", "pubDate": "2024-06-21 19:07:21", "link": "https://blog.centos.org/2024/06/centos-board-meeting-recap-june-2024/?utm_source=rss&utm_medium=rss&utm_campaign=centos-board-meeting-recap-june-2024", "guid": "https://blog.centos.org/?p=3189", "author": "shaunm", "thumbnail": "", "description": "The recording of the April CentOS Board meeting is now available. Watch the recording Read the minutes The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting: Davide created an \"Ask the CentOS Board\" Matrix room. Pat has documented the new SIG retirement […]", "content": "\n

The recording of the April CentOS Board meeting is now available.

\n\n

The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting:

\n\n", "enclosure": {}, "categories": [ "Uncategorized" ] }, { "title": "How to watch for CentOS Stream activity on Fedora Message Bus", "pubDate": "2024-06-05 10:42:19", "link": "https://blog.centos.org/2024/06/how-to-watch-for-centos-stream-activity-on-fedora-message-bus/?utm_source=rss&utm_medium=rss&utm_campaign=how-to-watch-for-centos-stream-activity-on-fedora-message-bus", "guid": "https://blog.centos.org/?p=3170", "author": "bookwar", "thumbnail": "", "description": "As you probably know, CentOS Stream development is happening in the open on Gitlab.com. You can see changes happening in real time in the redhat/centos-stream/rpms namespace. You can check open merge request, create yours and provide feedback. Yet, due to the limitations of the Gitlab platform, we have not been able to provide an unauthenticated […]", "content": "\n

As you probably know, CentOS Stream development is happening in the open on Gitlab.com. You can see changes happening in real time in the redhat/centos-stream/rpms namespace. You can check open merge request, create yours and provide feedback.

\n

Yet, due to the limitations of the Gitlab platform, we have not been able to provide an unauthenticated access to the feed of CentOS Stream events.

\n

We are now solving it by publishing all Gitlab events to the Fedora Message Bus.

\n

How to read messages

\n

Let's start with the interesting part first.

\n

Install the fedora-messaging package:

\n

$ sudo dnf install fedora-messaging

\n

Create a local copy of the configuration file:

\n

$ cp /etc/fedora-messaging/fedora.toml ./centos-integration-messaging.toml

\n

Change the routing_keys variable in the configuration file to subscribe to the topic org.centos.sig.integration:

\n

routing_keys = [\"org.centos.sig.integration.#\"]

\n

Run the client:

\n

$ fedora-messaging --conf ./centos-integration-messaging.toml consume

\n

The client will now listen to the topic on the message bus and will print all messages to the standard output.

\n

Of course you can do much more than just printing. For example, you can trigger a Jenkins job with the help of the AMQP Build Trigger, or you can develop your own application.

\n

Please check the Fedora Messaging documentation for more details.

\n

By the way, events from the CentOS Stream build system are also available on the Fedora Message Bus under the topic org.centos.prod.buildsys.

\n

How does it work

\n

There is a stateless application deployed to the CentOS SIGs Openshift cluster. A webhook on GitLab sends an event to the endpoint of the application, and it then translates the event into a message on the Fedora Message Bus.

\n

The sources are available in the gitlab-webhooks repository. And contributions are of course welcome.

\n

The service is maintained by the community under the umbrella of the CentOS Integration SIG.

\n

What's next

\n

We hope that the service will be useful for everyone who wants to build automation on top of the CentOS Stream.

\n

When you build such an automation - please let us know and consider joining the CentOS Integration SIG.

\n

We might be changing the messaging schema in the future to adopt a more strict message validation, and we would want to know your requirements.

\n

We also may expand the coverage and add events for other namespaces, such as, for example, events from CentOS SIG repositories.

\n", "enclosure": {}, "categories": [ "ci", "SIG", "fedora-messaging", "gitlab" ] }, { "title": "CentOS Infrastructure Update Q1 2024", "pubDate": "2024-05-27 09:21:37", "link": "https://blog.centos.org/2024/05/centos-infrastructure-update-q1-2024/?utm_source=rss&utm_medium=rss&utm_campaign=centos-infrastructure-update-q1-2024", "guid": "https://blog.centos.org/?p=3166", "author": "zlopez", "thumbnail": "", "description": "This is a summary of the work done by the CentOS Infrastructure team. This team maintains the infrastructure for both CentOS and CentOS Stream. This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading. About Purpose of this […]", "content": "\n

This is a summary of the work done by the CentOS Infrastructure team. This team maintains the infrastructure for both CentOS and CentOS Stream.

\n

This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.

\n

\n

\"\"

\n

About

\n

Purpose of this team is to take care of day-to-day business regarding CentOS and CentOS Stream infrastructure. It’s responsible for maintaining the services running in CentOS and CentOS Stream infrastructure and preparing for the new CentOS Stream release.

\n

Issue trackers

\n\n

Closed tickets

\n\n

Highlights

\n\n", "enclosure": {}, "categories": [ "Infra" ] }, { "title": "CentOS Board Meeting Recap, April 2024", "pubDate": "2024-04-12 22:34:00", "link": "https://blog.centos.org/2024/04/centos-board-meeting-recap-april-2024/?utm_source=rss&utm_medium=rss&utm_campaign=centos-board-meeting-recap-april-2024", "guid": "https://blog.centos.org/?p=3159", "author": "shaunm", "thumbnail": "", "description": "The recording of the April CentOS Board meeting is now available. Watch the recording Read the minutes The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting: The board discussed what to do with CentOS 7 AMIs after the CentOS 7 EOL. We […]", "content": "\n

The recording of the April CentOS Board meeting is now available.

\n\n

The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting:

\n\n", "enclosure": {}, "categories": [ "Board minutes" ] }, { "title": "Thanks to Equinix for sponsoring the CentOS Project", "pubDate": "2024-04-11 12:46:30", "link": "https://blog.centos.org/2024/04/thanks-to-equinix-for-sponsoring-the-centos-project/?utm_source=rss&utm_medium=rss&utm_campaign=thanks-to-equinix-for-sponsoring-the-centos-project", "guid": "https://blog.centos.org/?p=3154", "author": "Fabian Arrotin", "thumbnail": "", "description": "The CentOS Project , as long as I can remember, wouldn't have been possible without help of various sponsors over the years. Most sponsors listed on https://www.centos.org/sponsors sponsored one or more machines hosted in various datacenters over the globe, but some had a huge impact over the content delivery. Some years ago, Packet.net (now Equinix.com) […]", "content": "\n

The CentOS Project , as long as I can remember, wouldn't have been possible without help of various sponsors over the years.

\n

Most sponsors listed on https://www.centos.org/sponsors sponsored one or more machines hosted in various datacenters over the globe, but some had a huge impact over the content delivery. Some years ago, Packet.net (now Equinix.com) reached out to see how they'd be able to help us at the infra/network/bandwidth level and we agreed to use 4 machines in our mirror.centos.org (and from now on mirror.stream.centos.org pool) machines pool, itself seeding/feeding the whole external mirrors network

\n

I recently had a look at the collected stats/metrics from our zabbix monitoring solution and here is an interesting graph about these 4 machines (two in the USA - one on the east-coast and other on west-coast, one in Europe/Germany and last one in Asia/Japan) :

\n

\"\"

\n

From that graph (from the last 30 days) it's easy to guess when there is a new CentOS Stream compose going out (still happening for Stream 8 and Stream 9 when we'll publish this blog post), and also still CentOS 7 updates.

\n

That's without counting the various Special Interest Groups (SIGs) repositories which are maintained by community (and for the community).

\n

Thanks a lot Equinix for sponsoring these machines that really help getting new packages for the distributions but also SIGs content being delivered in a timely fashion to all our users

\n", "enclosure": {}, "categories": [ "Uncategorized" ] }, { "title": "CentOS Board Welcomes Troy Dawson", "pubDate": "2024-04-04 19:26:44", "link": "https://blog.centos.org/2024/04/centos-board-welcomes-troy-dawson/?utm_source=rss&utm_medium=rss&utm_campaign=centos-board-welcomes-troy-dawson", "guid": "https://blog.centos.org/?p=3149", "author": "shaunm", "thumbnail": "", "description": "CentOS is excited to welcome Troy Dawson to the Board of Directors. The CentOS Board is made up of 10 members, nominated by the community and appointed by a vote of the board. Celeste Lyn Paul decided not to serve another term this year, so the board began the process of selecting a new directory. […]", "content": "\n

CentOS is excited to welcome Troy Dawson to the Board of Directors.

\n

The CentOS Board is made up of 10 members, nominated by the community and appointed by a vote of the board. Celeste Lyn Paul decided not to serve another term this year, so the board began the process of selecting a new directory. We'd like to thank Celeste for her service and insights over the last two years. We had a lot of great nominations this time, and we'd also like to thank all the candidates for their willingness to serve, as well as the entire community for being engaged in the process.

\n

Troy works on the Emerging RHEL team at Red Hat, which looks at the future of RHEL based on Fedora and CentOS, as well as the CentOS Stream team, which handles the day-to-day maintenance of CentOS Stream. He's a well-known and longtime CentOS and Fedora contributor, having been a Fedora contributor for 12 years and a CentOS contributor for 7. Before working on CentOS, he was one of the co-founders of Scientific Linux.

\n

Troy is involved in a number of projects across the CentOS ecosystem. He's actively involved with EPEL, and has been an EPEL committee chair for almost four years. He's a member of the Fedora KDE SIG, which produces the Fedora KDE Plasma edtion. He's the chair and co-founder of the Alternative Images SIG, which is currently producing live CentOS images with both GNOME and KDE, and is working on adding more images. He's a member of the ISA SIG, which tests packages built with new CPU features enabled. And he was a co-founder of the original PaaS SIG, which worked on packaging OpenShift on CentOS (work that is now done in the Cloud SIG).

\n

If you've seen Troy at a conference, you probably saw him wearing one of his Hawaiian penguin shirts. He designs and makes these shirts himself in his side business, Casual Penguins.

\n

Troy's extensive experience, community involvement, and general friendliness will be a great addition to the board, and we look forward to working more closely with him.

\n", "enclosure": {}, "categories": [ "Uncategorized" ] }, { "title": "CentOS mailing lists migration to mailman3", "pubDate": "2024-04-03 12:15:24", "link": "https://blog.centos.org/2024/04/centos-mailing-lists-migration-to-mailman3/?utm_source=rss&utm_medium=rss&utm_campaign=centos-mailing-lists-migration-to-mailman3", "guid": "https://blog.centos.org/?p=3147", "author": "Fabian Arrotin", "thumbnail": "", "description": "Due to a needed upgrade , we'll have to move the existing CentOS mailman instance (aka https://lists.centos.org) to a new server/host. Migration is scheduled for \"\"\"\"Monday April 8th, 7:00 am UTC time\"\"\"\". You can convert to local time with $(date -d '2024-04-08 07:00 UTC') The expected \"downtime\" is estimated to ~60 minutes , time needed […]", "content": "\n

Due to a needed upgrade , we'll have to move the existing CentOS
\nmailman instance (aka https://lists.centos.org) to a new server/host.

\n

Migration is scheduled for \"\"\"\"Monday April 8th, 7:00 am UTC time\"\"\"\".
\nYou can convert to local time with $(date -d '2024-04-08 07:00 UTC')

\n

The expected \"downtime\" is estimated to ~60 minutes , time needed to :
\n- take last mailman2 backup
\n- reimport / convert mailman2 archives to mailman3 DB
\n- DNS propagation for A/AAAA/MX records

\n

Here are also some important information about the mailman2 => mailman3 migration :

\n

# Renamed lists
\nWorth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-March/165576.html), existing lists will be *renamed* , so while we'll put aliases for incoming mails, each list member will start receiving list mails from new list name. So start updating your filters if you filter on email address instead of \"subject:\"

\n

Here is the overview of the new lists names :

\n

arm-dev at centos.org => arm-dev at lists.centos.org
\ncentos at centos.org => discuss at lists.centos.org
\ncentos-devel at centos.org => devel at lists.centos.org
\ncentos-announce at centos.org => announce at lists.centos.org
\ncentos-automotive-sig at centos.org => automotive-sig at lists.centos.org
\ncentos-{cz,de,es,fr,nl,pt-br,zh}@centos.org => discuss-{cz,de,es,fr,nl,pt-br,zh}@lists.centos.org
\nci-users at centos.org => ci-users at lists.centos.org
\ncentos-gsoc: => gsoc at lists.centos.org
\ncentos-mirror at centos.org => mirror at lists.centos.org
\ncentos-mirror-announce at centos.org => mirror-announce at lists.centos.org
\ncentos-newsletter at centos.org => newsletter at lists.centos.org
\ncentos-promo at centos.org => promo at lists.centos.org
\ncentos-virt at centos.org => virt at lists.centos.org

\n

# Authentication
\nMailman2 had no real concept of authentication so you could just subscribe to one or more lists, and have a password associated with your email address for that/these subscription(s).
\nMailman3 itself is split into \"core\" and \"webui\" components, so when we'll import mailman2 lists/config into mailman3, your existing subscriptions will continue to work *but* not your password.

\n

Mailman3 will be configured to support SSO, and so if you already have a FAS/ACO account (https://accounts.centos.org) you'll be able to login directly into new webui and manage your settings/subscriptions *if* your ACO email address of course matches the one you initially subscribed with for lists.centos.org.

\n

If that's not the case, either create an ACO/FAS account that will match and you'll be then able to \"link\" your mailman3 account with FAS and so manage your settings/subscriptions.

\n

If you don't want to, there is always the documented process : https://docs.mailman3.org/en/latest/userguide.html#making-a-mailman-account

\n", "enclosure": {}, "categories": [ "Uncategorized" ] }, { "title": "March 2024 News", "pubDate": "2024-03-29 13:54:21", "link": "https://blog.centos.org/2024/03/march-2024-news/?utm_source=rss&utm_medium=rss&utm_campaign=march-2024-news", "guid": "https://blog.centos.org/?p=3144", "author": "shaunm", "thumbnail": "", "description": "March 2024 News CentOS Linux 7 and CentOS Stream 8 will both go EOL in just a couple months. Fabian Arrotin posted some details on how this will affect CentOS infrastructure. As a reminder, we have a blog post with EOL details and migration options. CentOS will migrate from Mailman 2 to 3 soon. Fabian Arrotin has asked […]", "content": "\n

March 2024 News

\n\n

Cloud SIG

\n

Packaging and maintaining different FOSS based Private cloud infrastructure applications that one can install and run natively on CentOS Stream.

\n\n

Storage SIG

\n

Purpose

\n

The CentOS Storage Special Interest Group (SIG) is a collection of like-minded individuals coming together to ensure that CentOS is a suitable platform for many different storage solutions. This group will ensure that all Open Source storage options seeking to utilize CentOS as a delivery platform have a voice in packaging, orchestration, deployment, and related work

\n

Releases

\n\n

Automotive SIG

\n

The Automotive SIG provides a center of gravity for CentOS automotive projects. The SIG produces three types of artifacts:

\n\n

AutoSD, or Automotive Stream Distribution, is a streaming distribution for automotive in-vehicle software development based on CentOS Stream. It is transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by many organizations who have commented or asked for help, so we know it is getting some traction though of course we don't have exact metrics on usage.

\n

Over the past year, we have done many things!

\n\n

In addition, there is a great deal of work in progress:

\n\n

Meetings are the first Wednesday of each month - please send email to jefro@redhat.com to be included on the invite. We hope you will join us!

\n", "enclosure": {}, "categories": [ "Uncategorized" ] }, { "title": "CentOS Board Meeting Recap, March 2024", "pubDate": "2024-03-28 15:27:53", "link": "https://blog.centos.org/2024/03/centos-board-meeting-recap-march-2024/?utm_source=rss&utm_medium=rss&utm_campaign=centos-board-meeting-recap-march-2024", "guid": "https://blog.centos.org/?p=3141", "author": "shaunm", "thumbnail": "", "description": "The recording of the March CentOS Board meeting is now available. Watch the recording Read the minutes The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting: There was some discussion on SIGs, including the SIG Council proposal (Issue 126) and the SIG […]", "content": "\n

The recording of the March CentOS Board meeting is now available.

\n\n

The recording has timestamps so you can skip to the parts that interest you. Here are a few highlights of the meeting:

\n\n", "enclosure": {}, "categories": [ "Board minutes" ] } ] }